In the identity view there are fields for entering the 窶廸ame窶, 窶廚ode窶 and 窶弑nit窶 attributes of a node.
The 窶廸ame窶 attribute obviously contains the name of the node. Since this is usually the attribute shown in the title field of the node, you should select a name that makes it easy for you to identify which variable the node represents. Apart from that there are no special rules.
The 窶廚ode窶 attribute can be used as a supplement to the 窶廸ame窶 attribute to further help you identify the variable. Again you are free to apply any coding system you like, or just ignore this field if you do not need it.
Note, however, that if you do not want to bother entering the code yourself, you can use the 窶彗utocode窶 feature. This option is controlled by using the 窶廸odes and events窶ｦ窶 command in the 窶弃reference窶 submenu of the 窶廡ile窶 menu. If the 窶廣uto code窶 option is checked, DynRisk will generate a code for you based on the code of the parent folder and the number of objects in this folder. In particular if you create a new node inside a folder with code 窶廣窶 and this node is the sixth object in this folder, the auto code for this node would be 窶廣.06窶.
In the 窶弑nit窶 field you specify the unit of the node. When you plot results from a simulation, the unit will show up on the plot axis. Thus, it is a good idea to enter the correct unit for each node. This, of course, makes your model easier to understand.
Note that if you are working on a model where all or most of the nodes have the same unit, you can save a lot of work by entering this unit as the default unit. This is done by using the 窶廸odes and events窶ｦ窶 command in the 窶弃reference窶 submenu of the 窶廡ile窶 menu.
The 窶廳ind窶 attribute, controlled by the corresponding popup menu is another optional identifier. DynRisk lets you choose between the following predefined kinds:
窶｢ General
窶｢ Boolean
窶｢ Category
窶｢ Constraint
窶｢ Cost
窶｢ Count
窶｢ Date
窶｢ Decision
窶｢ Duration
窶｢ Length
窶｢ Manhrs.
窶｢ Price
窶｢ Rate
窶｢ Volume
窶｢ Weight
窶｢ User 1
窶｢ User 2
窶｢ User 3
窶｢ User 4
If you do not need this attribute, just use 窶廨eneral窶 as kind. If you do not find anything appropriate, use 窶弑ser 1窶, 窶弑ser 2窶, 窶弑ser 3窶 or 窶弑ser 4窶, and replace this by something more suitable in your final risk analysis report.
The 窶廳ind窶 attribute can be used very effectively in conjunction with the 窶廡ind node窶ｦ窶 command in the 窶彜pecial窶 menu. You can e.g., very quickly make a list of all nodes of a particular kind in a model.
Another common use of the 窶廳ind窶 attribute is to identify date nodes.
Note that if you are working on a model where all or most of the nodes have the same kind, you can save a lot of work by selecting this kind as the default kind. This is done by using the 窶廸odes and events窶ｦ窶 command in the 窶弃reference窶 submenu of the 窶廡ile窶 menu.
The 窶彜ymbol窶 popup menu is used to control the appearance of the node, i.e., the node icon. Two options are available:
窶｢ Operator
窶｢ Kind
If you choose 窶廾perator窶, the node will have a circular icon with a symbol indicating its first operator or algorithm. This is useful if you want your graphs to reveal as much as possible of the mathematical structure of the model.
If you choose 窶廳ind窶, the node will have a square icon with a symbol indicating its kind. This is useful if you want to focus more on the qualitative sides of your model.
In addition to the attributes we have mentioned so far, the 窶廬dentity窶 view contains two more:
窶｢ Creation date
窶｢ Revision date
The creation date shows the date when the node was created, while the revision date shows the date for the last saved changes. If the model has not been saved on file since the node was created, you will only see a dash instead of a revision date.
For obvious reasons, the creation and revision dates cannot be edited.
